Summary

Fixes CON-5030: Continue Hub UI enters infinite render loop after deleting MCP server

Problem

When a user deleted their only MCP server, the UI could enter an infinite render loop if the deletion left behind:

• Orphaned references with missing properties
• Invalid/corrupted state data (undefined name, id, or array properties)
• Broken dependencies between UI components

Solution

Added multiple layers of defensive checks:

1. Redux Config Slice - Sanitize MCP server statuses on every config update

   • Filter out servers with missing/invalid id or name
   • Ensure all array properties exist (prompts, resources, errors, infos)

2. ToolsSection Component - Additional filtering in useMemo hook

   • Validate server structure before rendering
   • Use stable server.id as React key (fallback to name)

3. MCPServerPreview Component - Null-safe rendering

   • Add Array.isArray() checks before mapping
   • Provide fallback values for missing properties

Testing

• Verified changes compile without errors
• Code follows existing patterns and TypeScript types
• Defensive checks should prevent render loops even with corrupted data

Related

• Linear: CON-5030
• Slack: https://continuedev.slack.com/archives/C060AV775UZ/p1764632028752379

This agent session was co-authored by Karthik Chandra and Continue.

Summary by cubic

Prevents an infinite render loop in Continue Hub when MCP server data is deleted or corrupted. Addresses Linear CON-5030 by sanitizing config data and rendering only valid servers.

• Bug Fixes
  • Sanitize mcpServerStatuses in the Redux config slice; filter invalid servers and ensure arrays exist.
  • ToolsSection filters out malformed servers in useMemo and uses server.id as a stable React key (fallback to name).
  • MCPServerPreview adds Array.isArray checks and safe fallbacks for missing properties to avoid crashes.

^{Written for commit 19cf454. Summary will update automatically on new commits.}